![]() 10/24/2013 at 17:52 • Filed to: Kinja Help | ![]() | ![]() |
Today I tried to comment on a post and it said I needed to log in to comment. Well, I was logged in but went ahead and put in my screen name and key that they gave me (for a burner account) it said that the login was successful but then when I went back to try to comment I got the same "log in to comment" message. I tried numerous times and got the same result... any suggestions?
Edit: FIXED AT LAST!
![]() 10/24/2013 at 17:55 |
|
Edit your post and add "Kinja Help" as a tag. IT will see it. That doesn't help with your current problem, but it might get added to their punch list. I can't see my private view or my personal blog.
![]() 10/24/2013 at 18:12 |
|
Interestingly enough, I downloaded google chrome for iPhone and it works on here. Maybe it's a screw up with the built in Safari browser, who knows.
![]() 10/24/2013 at 18:28 |
|
I'm using my iPhone right now. You might want to clear cookies and data and try again.
![]() 10/24/2013 at 18:29 |
|
Hi PTS- it's likely a local cache issue. Try clearing Safari's cookies/cache and restarting the browser. That should get you logged in.
![]() 10/24/2013 at 19:10 |
|
I tried that a couple times and it didn't work, even after turning my phone on and back off. It says that the login is successful and then reloads the page that says that I need to log in, and then that automatically bounces me back to the login window.
![]() 10/24/2013 at 22:18 |
|
![]() 10/24/2013 at 23:49 |
|
Wow. I had the same problem and solution as you.
![]() 10/25/2013 at 10:55 |
|
We released some improvements this morning that should smooth out a lot of these login issues that lingered yesterday. Have you noticed any improvement?
![]() 10/25/2013 at 11:33 |
|
Yes, I managed to get it to work on the built in Safari app by clicking the option to create a new burner account which redirected me to a different page where I then logged in as I would have before, and that fixed the problem.
![]() 10/25/2013 at 11:35 |
|
If you haven't gotten it fixed yet for safari, look in the conversation with Ernie. He said they made some improvements but if that doesn't work, you can try the solution I found.